5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
- Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-1: ILF Integration

Event Point Definition and Description


Event points are defined to correspond to the nature of a process or process component. For example, an image has a Pre-Display event point, while a frame has a corresponding Start of Frame event point. Input processes also have a Post PCF Update event point, although a menu process does not because a menu does not update a process control file. As a result, while each process type/component has a unique set of event points, there is a consistent pattern throughout the system.

Another item to note is that some event points may not occur in certain instances, depending on what you specified the process to do. For example, a frame may or may not have an image associated with it. If the frame produces an image, it has a Pre-Display event point; if no image is produced, the Pre-Display event point is not available. As a result, the applicable set of event points for a process is dependent upon the context in which you specify it.

Refer to Using Event Points for details on event point timing and usage.

Application Design Manual                                         "Powered by Appx Software"

511

©2006 By APPX Software, Inc. All Rights Reserved